chore: revert manifest version bump — keep at scaffold starter (0.1.0)#28
Merged
Merged
Conversation
The version field in a template manifest is the scaffold starter version that new projects inherit when generated from the template, not the template's own release version. Bumping it to 1.0.0 in #27 meant any project scaffolded after that PR would start at 1.0.0 instead of 0.1.0, defeating the purpose of a clean baseline. Reverts pyproject.toml to 0.1.0. The template's release history is still tracked via git tags and GitHub Releases — the v1.0.0 tag will be re-pointed to the post-revert HEAD so `git checkout v1.0.0` also gives a 0.1.0 manifest.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The
versionfield in a template manifest is the scaffold starter version new projects inherit when generated from the template, not the template's own release version. Bumping it to 1.0.0 in #27 was incorrect: any project scaffolded after that PR would start at 1.0.0 instead of 0.1.0, defeating the purpose of a clean baseline.Reverts
pyproject.tomlback to0.1.0.The template's release history is still tracked via git tags and GitHub Releases (see the
v1.0.0release). After this merges, thev1.0.0tag will be force-updated to the post-revert HEAD so checking outv1.0.0also gives a0.1.0manifest — the manifest stays decoupled from release versioning, consistently, at every ref.